Skip to content

Plane-EE: Update Plane version to v1.9.3 and add email service configuration in README#107

Merged
mguptahub merged 3 commits intodevelopfrom
add-email-readme
May 22, 2025
Merged

Plane-EE: Update Plane version to v1.9.3 and add email service configuration in README#107
mguptahub merged 3 commits intodevelopfrom
add-email-readme

Conversation

@akshat5302
Copy link
Member

@akshat5302 akshat5302 commented May 22, 2025

Description

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Improvement (change that would cause existing functionality to not work as expected)
  • Code refactoring
  • Performance improvements
  • Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

  • New Features

    • Added configuration options for deploying and customizing an email service, including resource limits, Docker image settings, and SMTP domain support.
    • Enabling the email service will now automatically create a cert-issuer for TLS certificates.
  • Improvements

    • Updated default Plane version to v1.9.3 across documentation and configuration files.
    • Added an option to set the image pull policy for the email service, defaulting to "Always".
  • Documentation

    • Updated documentation to reflect new version and added a dedicated section for email service deployment and configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 22, 2025

Warning

Rate limit exceeded

@akshat5302 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 4 minutes and 30 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 23e601f and 90f1763.

📒 Files selected for processing (4)
  • charts/plane-enterprise/Chart.yaml (1 hunks)
  • charts/plane-enterprise/README.md (4 hunks)
  • charts/plane-enterprise/questions.yml (1 hunks)
  • charts/plane-enterprise/values.yaml (2 hunks)

Walkthrough

This update increments the Plane version from 1.9.2 to 1.9.3 across chart metadata, documentation, and configuration files. It introduces a configurable image pull policy for the email service deployment and documents new email service deployment options in the Helm chart README.

Changes

File(s) Change Summary
charts/plane-enterprise/Chart.yaml, charts/plane-enterprise/questions.yml, charts/plane-enterprise/values.yaml Updated Plane version references from 1.9.2 to 1.9.3; added email service image pull policy configuration.
charts/plane-enterprise/README.md Updated version references; added documentation for email service deployment configuration and cert-issuer note.
charts/plane-enterprise/templates/workloads/email.deployment.yaml Added dynamic imagePullPolicy field to email service deployment template.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Helm
    participant Kubernetes
    participant EmailService

    User->>Helm: Install/Upgrade Plane Chart (v1.9.3)
    Helm->>Kubernetes: Apply manifests (with email service config)
    Kubernetes->>EmailService: Deploy container (with imagePullPolicy)
    EmailService-->>Kubernetes: Pull image (Always or as configured)
Loading

Possibly related PRs

Suggested reviewers

  • mguptahub
  • pablohashescobar

Poem

A hop, a skip, a version jump—
Now 1.9.3, we thump!
Email service, pull with glee,
Docs refreshed for all to see.
Chart and values, all aligned,
🐇 Helm deploys, with peace of mind!


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd957ba and 23e601f.

📒 Files selected for processing (5)
  • charts/plane-enterprise/Chart.yaml (1 hunks)
  • charts/plane-enterprise/README.md (4 hunks)
  • charts/plane-enterprise/questions.yml (1 hunks)
  • charts/plane-enterprise/templates/workloads/email.deployment.yaml (1 hunks)
  • charts/plane-enterprise/values.yaml (2 hunks)
🔇 Additional comments (8)
charts/plane-enterprise/questions.yml (1)

23-23: Plane version default updated

The planeVersion default is correctly bumped to v1.9.3, matching the appVersion in Chart.yaml.

charts/plane-enterprise/values.yaml (2)

1-1: Plane version updated

The top-level planeVersion is now v1.9.3, aligning values with the chart metadata and questions default.


160-160: Add email service pullPolicy

Introducing services.email_service.pullPolicy: Always ensures that the email service image is refreshed on each deployment, consistent with other services’ pull policies.

charts/plane-enterprise/templates/workloads/email.deployment.yaml (1)

50-50: Set imagePullPolicy for email container

The imagePullPolicy is now driven by services.email_service.pullPolicy with a default of "Always", matching the pattern used across other service deployments.

charts/plane-enterprise/README.md (4)

14-14: Update example command Plane version

The example export now uses PLANE_VERSION=v1.9.3, which aligns with the chart and values changes.


68-68: Update minimum setup values

The required planeVersion in the quick-start bullet list is correctly updated to v1.9.3.


103-103: Refresh license table entry

The license table now references planeVersion | v1.9.3, consistent with other documentation updates.


289-302: Document Email Service Deployment

The new "Email Service Deployment" section clearly outlines the services.email_service.* keys, including pullPolicy, and the required env.email_service_envs.smtp_domain. The note about automatic TLS cert-issuer creation is informative.

Comment on lines +8 to +9
version: 1.2.3
appVersion: "1.9.2"
appVersion: "1.9.3"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Chart version bump missing

You've updated the appVersion to "1.9.3" but left the chart version at 1.2.3. According to Helm best practices, the chart version should be incremented with every change to chart metadata or defaults to allow proper version tracking and publishing.

Apply this diff:

-version: 1.2.3
+version: 1.2.4
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
version: 1.2.3
appVersion: "1.9.2"
appVersion: "1.9.3"
version: 1.2.4
appVersion: "1.9.3"
🤖 Prompt for AI Agents
In charts/plane-enterprise/Chart.yaml at lines 8 to 9, the chart version is
still set to 1.2.3 despite updating the appVersion to 1.9.3. To fix this,
increment the chart version to a higher value (e.g., 1.2.4) to reflect the
change in chart metadata, ensuring proper version tracking and compliance with
Helm best practices.

@mguptahub mguptahub merged commit 21a680f into develop May 22, 2025
3 checks passed
@mguptahub mguptahub deleted the add-email-readme branch May 22, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants